Clarify the public core and sustainable support model - #4

Purpose

This PR does not change the Foundation's technical direction, governance model, implementation boundaries, production systems, or program commitments. It consolidates existing commitments into one clearer public entry point for developers, implementers, contributors, sponsors, and institutional partners.

What this clarifies

• ICSN remains the implementation-neutral public standards program.
• People and legal entities retain control of portable, interoperable identity, credentials, data, agents, records, and authorized assets.
• Foundational IAM remains a no-charge public-infrastructure commitment.
• The standalone capability profile does not require an M5 connection; its promised open-license release is stated separately from the current public-review license status.
• M5Core and the Freedom Office remain an optional reference implementation rather than the owner of ICSN.
• Finance, ledgers, payments, social systems, registries, and other services are optional integration layers.
• The first 100 provide the reference activation environment for the goal of supporting up to 100,000 women-led ventures.
• Sponsors, contributors, implementers, reviewers, and partners are essential to sustaining the public core.
• Funding does not purchase standards authority, private participant data, or control of owner-held assets.

Scope boundary

This PR changes only profile/README.md. It does not change schemas, licenses, databases, production services, participant records, pricing, or financial workflows. Higher-level opportunities use only the Foundation contact email.

Verification

• Confirmed every linked standards-repository file exists on main.
• Confirmed the public IAM endpoint returns HTTP 200.
• Confirmed the README contains no investment, pricing, minimum, or economic-return language.
• Ran git diff --check.

Follow-up work, not included here

1. Publish the expressly open-license standalone M5-CV/capability-template release.
2. Prepare the M5Core/Freedom Office technical architecture as a separately reviewed technical contribution.
3. Update repository-setting descriptions after this public wording is approved.
4. Add GitHub Sponsors funding metadata only after the Sponsors profile is active.